Release notes for WebAPI 3.12.0.4301

Bug fixes

  • The Media Viewer in Axiell Collections did not display any PDF files in the Media Viewer if the WebAPI was used as the image handler. Fixed in 3.11.1.4297.

  • Some searches were slow if the search result was automatically sorted on a largely empty column (the k column) in the relevant SQL table. The fix in build 3.11.1.4291 makes sure that sorting on the k column (which is required for hierarchies) is only done when it is actually filled with values to sort on. If not, the default sorting is done on the priref column. When a query is executed with a given sort field (like sorting on a column in the result set), that field will still be used for sorting and not the k column or priref column.

  • When part_of_reference.lref was updated with a JSON Payload and indexed links applied to this linked field, then the parent was removed from the updated child record. Fixed in version 3.11.1.4289.

  • A Sequence contains no matching element error could appear when <reportDeletedRecords>true</reportDeletedRecords> was set in the configuration, because the associated check in the software to see if journalling was enabled for the configured database(s) did not work correctly. This was fixed in build 3.11.1.4281.

  • WebAPI CPU usage was peaking after a period of inactivity, with an Object reference not set... error. Fixed in version 3.11.1.4247.

  • When updating a record using the WebAPI, the creation date would have been updated too. Fixed in 3.11.1.4212.

  • The part_of_reference.lref field was not written in case of hierarchical indexed links so the link was not correctly written. This also meant you could write a non-existing record into a hierarchical link. This was fixed in 3.11.1.4205. With the fix, the WebAPI will now refuse writing a link to a non-existing record with a message in the diagnostics section of the XML response, saying something like: 
    <error>
     <message>Linked record not found for database 'collect', part_of_reference.lref[1] with data '10'</message>
    </error>